i think this needs to be a more critical response than an avoidance. i.e. we need to fix when this happens. so i would suggest not merging this, but instead using something like this to add to the admin dashboard, so that we know what to fix. the silent suppression that this does is not going to be helpful.

I'm merging this for now because all it does is restore the status quo that existed up until a few days ago.

so i would suggest not merging this, but instead using something like this to add to the admin dashboard, so that we know what to fix.

It seems like we already track invalid assets, we just need to improve the dashboard for it (#1197). Are you asking for something different? In general, I would like it if dandi-schema provided a better way of distinguishing between genuinely exceptional events and problems with client provided metadata (dandi/dandi-schema#127 (comment)).

🚀 PR was released in v0.3.15 🚀

i think this would result, for any landing page to not show anything in the asset summary. this would only be detected when someone goes on the landing page, rather than fixing the core issue of assets. hence i wanted a more severe restriction that when this happens, we should, as dandi, fix the issue as fast as possible. in most cases this is not a user issue. more often a dandi issue.